Offline voicemail

ABSTRACT

A method for accessing offline voicemail messages within a mobile messaging application may be provided. First, a voice mail message may be received and the voicemail message may be transcribed to text. Next, the voicemail message and the text transcription may be stored. The recipient may then be presented with a list of voicemail messages and the voicemail message may be retrieved in response to the recipient. The recipient may read or listen to the voicemail message or both. The recipient may also annotate the voicemail message.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation application of U.S. patentapplication Ser. No. 13/647,225, entitled “OFFLINE VOICEMAIL,” filed onOct. 8, 2012, which is a continuation application of U.S. patentapplication Ser. No. 12/239,994 (now U.S. Pat. No. 8,284,909), entitled“OFFLINE VOICEMAIL,” filed on Sep. 29, 2008, the entire disclosures ofwhich are hereby incorporated herein by reference.

BACKGROUND

Voicemail is a system for managing telephone messages. Conventionalsystems are problematic from a recipient experience perspective in anumber of instances. Firstly, the recipient may have to dial-in to checkvoicemail messages. Dialing in to check voicemail messages takes timeand is not appropriate in a number of social contexts when a phone callcannot be made. Secondly, interfaces are often serialized and requirelistening to all voicemail messages in order, without regard topriority. Thirdly, there is a lack of integration with othercommunication modes (i.e., replying to a voicemail with an email is notsupported.) And fourthly, a model to take notes or add context to thevoicemail message is not available.

SUMMARY

This Summary is provided to introduce a selection of concepts in asimplified form that are further described below in the DetailedDescription. This Summary is not intended to identify key features oressential features of the claimed subject matter. Nor is this Summaryintended to be used to limit the claimed subject matter's scope.

A method for accessing offline voicemail messages within a mobilemessaging application may be provided. First, a voice mail message maybe received and the voicemail message may be transcribed to text. Next,the voicemail message and the text transcription may be stored. Therecipient may then be presented with a list of voicemail messages andthe voicemail message may be retrieved in response to the recipient. Therecipient may read or listen to the voicemail message or both. Therecipient may also annotate the voicemail message.

Both the foregoing general description and the following detaileddescription provide examples and are explanatory only. Accordingly, theforegoing general description and the following detailed descriptionshould not be considered to be restrictive. Further, features orvariations may be provided in addition to those set forth herein. Forexample, embodiments may be directed to various feature combinations andsub-combinations described in the detailed description.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings, which are incorporated in and constitute apart of this disclosure, illustrate various embodiments of the presentinvention. In the drawings:

FIG. 1 is a block diagram of an operating environment;

FIG. 2 is a flow diagram of a method of accessing an offline voicemailmessage;

FIG. 3 is an illustration of a recipient interface;

FIG. 4 is the illustration of the recipient interface in FIG. 3 in moredetail;

FIG. 5 is a flow diagram of a method of playing and downloading avoicemail message file; and

FIG. 6 is a block diagram of a system including a computing device.

DETAILED DESCRIPTION

The following detailed description refers to the accompanying drawings.Wherever possible, the same reference numbers are used in the drawingsand the following description to refer to the same or similar elements.While embodiments of the invention may be described, modifications,adaptations, and other implementations are possible. For example,substitutions, additions, or modifications may be made to the elementsillustrated in the drawings, and the methods described herein may bemodified by substituting, reordering, or adding stages to the disclosedmethods. Accordingly, the following detailed description does not limitthe invention. Instead, the proper scope of the invention is defined bythe appended claims.

FIG. 1 is a block diagram of an operating environment setting forth thegeneral environment involved in a messaging system 100 consistent withembodiments of the present invention. System 100 may enable a sender,using a sender device 101, to send a voicemail message to a server 102.Consistent with embodiments of the present invention, sender device 101may comprise any device capable of sending and receiving messages and isnot limited to a mobile telephone or a personal computer (PC). Server102 may comprise any server capable of transcribing the voicemailmessage from speech to text. Server 102 may also be capable of storingtranscribed voicemail messages, providing notifications of missed callsand voicemail messages to a recipient, receiving annotated messages, andsynchronizing voicemail messages with a recipient device 103.

After server 102 receives the voicemail message from sender device 101and transcribes the voicemail message, recipient device 103 maydownload, store, and present a recipient with the voicemail message andtext transcription. Recipient device 103 may be, but is not limited to,a client computer or a mobile device such as a mobile telephone orpersonal data assistant (PDA). Recipient device 103 may allow therecipient to deal with voicemail messages without the recipient havingto dial-in to a service or listening to the voicemail message.

FIG. 2 is a flow diagram setting forth the general stages involved in amethod 100 consistent with an embodiment of the invention for accessingoffline voicemail messages. Method 200 may be implemented using acomputing device 600 as described in more detail below with respect toFIG. 6. Ways to implement the stages of method 200 may be described ingreater detail below. Method 200 may begin at starting block 201 andproceed to stage 202 where a phone system (not shown) may receive avoicemail message or a missed call notification from a sender. The phonesystem may be integrated with server 102. For example, when the senderplaces a call to the recipient and the call is missed, instead of thevoicemail message or the missed call notification being left on arecipient's phone mailbox (the recipient's phone comes with an offlinevoicemail mailbox), the voicemail message may go to the server'smailbox. When receiving the voicemail message or the missed callnotification, server 102 may recognize a telephone number or the senderand generate the sender's information. Generating the sender'sinformation comprises at least one of the following: searching, fetchingand providing an electronic mail address, searching, fetching andproviding a physical address, searching, fetching and providing awebsite link, and searching, fetching and providing other configuredinformation about the recognized number or the recognized sender.

From stage 202, where server 102 received the voicemail message, method200 may advance to stage 203 where the server 102 may store thevoicemail message in the server mailbox. After stage 203, method 200 mayproceed to stage 204 where exchange voicemail messages (EVMs) areautomatically transcribed to text on server 102. EVMs are voicemailsstored on server 102. At stage 205, the EVM and the text transcriptionare integrated. The integration of the text transcription and the EVMcomprises allowing a recipient to switch from text transcription to theEVM. Switching from the text transcription to the EVM comprisesselecting a point in the text transcription and playing the EVM from theselected point in the text transcription. The test transcription and theEVM may be encrypted during this process.

During the transcribing of the EVM to text, method 200 may denoteunrecognized voicemail speech in the EVM with at least one of thefollowing: font, color, and size. After stage 204, method 200 mayproceed to stage 205 where the EVMs and the text transcriptions arestored. After server 102 stores the voicemail message at stage 205,method 200 may continue to stage 206 where recipient device 103 maydownload emails and voicemail messages from server 102. Recipient device103 may download emails from server 102 that may also contain voicemailmessages in the form of an email.

After stage 206, method 200 may proceed to stage 207 where the recipientmay be notified that EVMs and missed calls are available. Thenotifications distinguish offline voicemail messages from conventionalvoicemail messages that a phone operator may provide. The recipient mayalso be notified of missed calls when recipient device 103 is connectedto server 102. For example, there may be missed calls when the recipientis offline that may be stored on server 102. When recipient device 103is later connected with server 102, the missed calls may be sent torecipient device 103.

The voicemail messages and the missed calls may be integrated into anotification system as follows. For both voicemail messages and missedcalls, they may each have their own notification type. The voicemailmessages and the missed calls may not be counted as part of a new emailnotification. Voicemail and missed call notifications may be dismissedif the recipient goes to a voicemail pivot. (See example 3 below formore details.)

Single voicemail and missed call notifications may take the recipientdirectly to a specific interface. Whereas, multiple voicemail and missedcalls notifications may take the recipient to the voicemail pivot.

EXAMPLE 1 Single Voicemail Notification

A single voicemail may prompt a single voicemail notification. FIG. 3 isan illustration of a recipient interface. The recipient can click onsingle voicemail notification by clicking on “View” on a soft key 340and is taken to the recipient interface. The voicemail notification maybe dismissed upon taking the recipient to the recipient interface.

EXAMPLE 2 Single Missed Call Notification

This is just like the prior scenario, just with a special missed callnotification and icon.

EXAMPLE 3 Mixed Mode (A Single Voicemail Messages, Multiple MissedCalls, and Multiple Electronic Mails)

There may be three different notifications: (1) A notification forvoicemail message (clicking “View” may take recipient to the recipientinterface, and may only dismiss the voicemail notification); (2)Multiple missed calls notification (clicking “view” may take therecipient to the voicemail pivot, may dismiss both the voicemail and themissed call notification because the recipient may be taken to thevoicemail pivot/list view); and (3) multiple email notifications(clicking “view” may take the recipient to an “unread” pivot, this maydismiss all three notifications because the recipient can see all themessages.)

EXAMPLE 4 Mixed Mode (Multiple Voicemail Messages, Multiple ElectronicMails)

This is a variation on Example 3 above. There may be two differentnotifications: (1) Multiple voicemail notification (clicking “View” maytake the recipient to the Voicemail pivot, only the voicemailnotification may be dismissed) and (2) Multiple email notification(clicking “view” may take the recipient to the Unread pivot, bothvoicemail and email notifications may be dismissed.)

Once the recipient is notified that the EVMs and/or the missed calls areavailable in stage 207, method 200 may continue to stage 208 where therecipient may be presented with a list of voicemail messages. Therecipient may also be presented with an interface for the recipient tointeract with. The interface presented may comprise previewing a texttranscript, listening to the EVM, deleting the EVM, replying to the EVM,flagging the EVM, or calling back a telephone number from the EVM. Thelist of EVMs may also be sorted and presented based on a sender or apredetermined context that the recipient has identified.

The presentation of the list of voicemails may be designed to includeEVM and missed calls. When the EVM is not linked to other messages, theicon used may be unique. When the EVM is part of a message with morethan one message, then the rolled up message may show a standardconversation icon. When the recipient clicks on the message and itexpands, then the unique voicemail icon may be displayed next to theEVM.

After the EVMs are presented in stage 208, method 200 may proceed tostage 209 where server 102 may receive a request to retrieve aparticular EVM from the recipient.

After the receiving the request to retrieve the EVMs at stage 209,method 200 may proceed to stage 210 where the EVMs or the missed callsare retrieved based upon the recipient's request. The EVM may beretrieved from server 102 or recipient device 103 without dialing into aservice. After retrieving the EVMs at stage 210, method 200 proceeds tostage 211 where the recipient may open the EVMs. A User Interface (UI)300 may be displayed when the recipient opens the EVM which is discussedin FIG. 3 below. The recipient may open the voicemail message just asthe recipient would open a traditional email message.

In another embodiment of the invention, recipient device 103 may beconfigured to automatically retrieve particular EVMs based on aconfigured request, by the recipient, to retrieve particular EVMs. Basedon the recipient's configuration, the request may be automaticallyretrieved from recipient device 103 and then presented to the recipientat stage 208.

After opening the EVM at stage 211, the method 200 may proceed to stage212 where the recipient may be able to play audio of the EVM. The EVMmay include integrated play controls that let the recipient play, pause,fast forward, or reverse through the audio portion of the voicemailwhile remaining in the context of a messaging application. The recipientmay also download the EVM when available to the recipient. Downloadingthe EVM audio file while playing is discussed later with respect to FIG.5 below. The recipient may play or replay any part of the audio byselecting the associated text in a text transcription.

After opening the EVM at stage 211, the method 200 may proceed to stage213 where the recipient may be able to read the EVM. If the texttranscription of the EVM is available, the recipient can read throughthe text version, or the recipient can play the EVM inline and listen tothe EVM. If at some point the recipient would like to listen to the EVMwhile reading it, the recipient may switch to the EVM by selecting theassociated text in the text transcription. The recipient may decide toplay a particular portion of the text transcription or replay any partof the audio by selecting the associated text in the text transcription.

The EVM text transcription may include a reading form similar to atraditional email message. The reading form may include detailed calleridentification (callerID) information. The reading form may also includeintegrated play controls that let the recipient play, pause, fastforward, or reverse through the audio portion of the voicemail whileremaining in the context of a messaging application. The reading formmay be integrated between the EVM, email and text messagingapplications. This integration may enable the recipient to smoothlytransition between communication modes on recipient device 103.

After stage 211 where the recipient opens the EVM, stage 212 where therecipient plays the EVM, or stage 213 where the recipient reads the EVM,method 200 may proceed to stage 214 where the recipient may take downsome notes to associate it with a particular EVM. From stage 214, wherethe recipient takes down some notes, method 200 may advance to stage 215where the notes may be attached and stored to the EVM.

From stage 215 where the recipient may attach and store the notes to theEVM, method 200 may proceed to stage 216 where recipient device 103 maytry to connect to server 102. If there is a connection available, method200 may proceed to stage 217 where the annotated voicemail message maybe synchronized with the server and the method may end at stage 218.

If a connection is not available to sever 102 at stage 216, theannotated voicemail message may be saved locally on recipient device 103until there is a connection to synchronize server 102. Recipient device103 may not be able to connect with server 103 because recipient device103 may not be in a location that is able to connect with server 102. Asa result, the annotated EVM may be saved locally on recipient device102. After stage 216, the method 200 may end at stage 218.

After stage 211 where the recipient opens the EVM, stage 212 where therecipient plays the EVM, stage 213 where the recipient reads the EVM, orstage 214 where the recipient annotates the EVM, method 200 may advanceto stage 219 where the recipient may reply or forward the EVM. Therecipient may reply or forward the EVM as an email message based on thetranscription, or the recipient can callback the sender based on a phonenumber displayed. At stage 219, when the recipient replies or forwardsthe EVM, the recipient may send a mobile message to another recipientbased on the phone number or the sender information that recipientdevice 103 received because the voicemail message can be treated as anemail. The mobile message, may be, but is not limited to short messageservice (SMS), multimedia messaging service (MMS), or email.

When the recipient replies as the email, a full transcript can be shownand sent to other recipient(s). If the recipient decided to forward thevoicemail message as an email, the recipient of the forwarded email mayget both the text transcript and the original EVM. The recipient of theforwarded EVM may either read the text transcript, listen to the EVM, orboth. That is, while the recipient of the forwarded EVM is reading thetext transcript, the recipient can switch to play the EVM like theoriginal recipient. All the functions that may have been available tothe original recipient may also be available to the forwarded emailrecipient.

As stated above, FIG. 3 illustrates a recipient user interface (IU) 300.UI 300 may comprise a header section 310 and a body 320. UI 300 may alsoinclude a message progress bar 330 that may be used to give visualqueues to the recipient about any audio content the EVM may have. UI 300may also have soft keys 340 that may display actions the recipient maybe allowed to perform.

Header section 310 may display as much relevant information about thecaller. FIG. 4 is an example of UI 300 with more details in header 310,body 320, progress bar 330, and soft keys 340. As shown in FIG. 4, UI300 displayed on recipient device 103 may include: a sender/from field410, a subject 420, and a date and time the voicemail message wasreceived. By default, when UI 300 is opened, the caller's name (e.g. insender/from field 410) and subject 420 may be displayed.

When the recipient opens UI 300, there may be several differentscenarios that sender/from field 410 may accommodate. They include: (1)anonymous caller when there is no-caller information available for thesender, (2) a phone number when the phone number information isavailable, but it is not on server 102 or the recipient's contact storeon server 102, (3) a sender name if the phone number resolved againstthe recipient's contact store on server 102, and (4) the sender's nameand full contact card if the sender is resolved against the recipient'slocal contacts.

Subject 420 may include the type of device, who the original EVM wassent from, and the length of time of the EVM. The date and time stampmay be not visible on the screen, but may be above header 310. When anaudio file is attached to the EVM, the audio file may be suppressed(e.g. not visible in header 310.) The recipient may use soft keys 460 toplay the EVM or delete the EVM.

There may be two cases where a voicemail file may have more than oneattachment. The first case may be when the recipient adds a file to theexisting voicemail message. When there are more files (e.g. non EVMfiles) attached to the message, those attachments may not be suppressedor hidden in the card, but they may be displayed in UI 300 as anattachment 430 in the header. For example, if the recipient wanted toattach a budget document or the like to the EVM, the attachment may bedisplayed as attachment 430 in FIG. 4. Recipient device 103 may allowthe recipient to add additional attachments to an existing EVM. UI 300form may have the same type of logic to only display attachment 430 ifthe recipient has more than one attachment on the file.

The second case may be when the EVM may be forwarded or replied to withan existing EVM. In such a situation, the recipient may call into avoice access to forward or reply to the EVM. The voice access may thenallow the recipient to add a voice introduction. When this happens,server 102 or recipient device 103 may stamp a priority attribute onboth audio file attachments, so that recipient device 103 and the voiceaccess may know what order to play the files.

UI 300 may continue to suppress the UI audio attachments 430. When theEVM plays, the total duration of all EVM audio files may be calculated.The total length can be displayed in the progress bar 330 and played insequential order. The duration for the most latest audio file that wasappended to the message may be sent, so recipient device 103 cancalculate the total duration of all audio files when they are loaded.

Body section 320 may comprise two parts as shown in FIG. 4. The twoparts may be voicemail notes 440 and a voicemail text transcription 450.Body section 320 may be subject to a truncation limit, in which case, itmay display a link to download rest of the EVM. Notes 440 informationmay be truncated if it exceeds a predetermined size. The predeterminedsize limit may be enforced by server 102 or recipient device 103. Ifbody section 320 contents go beyond a screen height, then the recipientmay scroll the screen to view all of body section 320 contents.

Message progress bar 330 may always be displayed when UI 300 is openedas discussed above in FIG. 2 at stage 211. The presence of progress bar330 may help the recipient to understand that the EVM may be availableand to prevent choppiness when shifting between stop/pause and play. Ifbody section 320 contents go beyond the screen height, then therecipient may scroll the screen, but message progress bar 330 may remainin the same position.

Messaging progress bar 330 may be based on priority and ranking. Forexample, types of progress bars 330 with higher rankings may bedisplayed above other progress bars. For example, in the case of a“Playing” and “Downloading” progress bar, the “Playing” progress bar maybe registered with a higher ranking than the “Downloading” progress bar.

FIG. 5 is a flow chart setting forth the general stages involved in amethod 500 consistent with an embodiment of the invention to seamlesslyswitch between two progress bars in the case where recipient device 103may need to fetch the rest of the EVM audio file. Method 500 may beimplemented using a computing device 600 as described in more detailbelow with respect to FIG. 6. Ways to implement the stages of method 500may be described in greater detail below. Method 500 may begin atstarting block 505 and proceed to stage 510 where the recipient mayclick “Play” on the soft key 460 to play the EVM. When the recipiententers into UI 300, the recipient may see progress bar 330, which mayprovide a visual hint that there is an EVM to be listened. There may bea left and right status, but at the state when UI 300 was opened, theleft status may be 00:00 and the right status may have the totalduration of the audio file. The total duration may be formatted asmm:ss.

From stage 510, after the recipient clicked “Play” to play and listen tothe voicemail message, method 500 may advance to stage 520 whererecipient device 103 may try to open the EVM file on the recipientdevice 103. From stage 510, if the EVM file is present on recipientdevice 103, the method 500 may proceed to stage 580 where the full EVMaudio file may be played. From stage 510, if the EVM file is notpresent, the method 500 may proceed to stage 530 where the “Downloading”progress bar may be displayed behind the “Playing” progress bar. If the“Playing” progress bar has a higher priority, it may always be displayedin front of the “Downloading” progress bar. This approach may help givethe impression that it's the same bar but the status may inform therecipient that the EVM file is downloading.

From stage 530, the method 500 proceeds to stage 540 where the EVMdownload may be initiated. From stage 540, the method 500 proceeds tostage 550 where the “Playing” progress bar may be removed and the“Downloading” progress bar may be displayed. The recipient may see theleft status change to “Downloading” and the right status may then givethe total size of the download. The recipient may have the option ofcanceling the download by clicking “cancel” on soft key 340.

From stage 550, the method 500 may proceed to stage 560 where recipientdevice 103 may determine whether the EVM file has been downloadedsuccessfully. If the voicemail message file is downloaded successfullythe method 500 may proceed to stage 580 where the method 500 may playthe full EVM file. Once the voicemail message file has been downloaded,the audio file may begin playing through speaker phones. The recipientcan click “speaker on” on soft key 340 to project the sound through anexternal speaker. When the voicemail message is playing, the recipientmay advance through the message or go back using the left and rightbuttons. The recipient may also decide to play a particular portion ofthe EVM and start playing the EVM at that or any point in the EVM. Therecipient may further decide to skip around the EVM by clicking ondifferent portions of the text transcription. After stage 580, wheremethod 500 played the voicemail message file, method 500 may end atstage 590.

If the file download is unsuccessful, method 500 may proceed to stage570 where the recipient is informed that recipient device 103 is unableto connect to server 102. And after stage 570, method 500 may end atstage 590.

An embodiment consistent with the invention may comprise a system foraccessing offline voicemail messages. The system may comprise a memorystorage and a processing unit coupled to the memory storage. Theprocessing unit may be operative to receive a voicemail message,transcribe the voicemail message to text, store the voicemail message,present a recipient with a list of voicemail messages, retrieve thevoicemail message, and allow a recipient to annotate the voicemailmessage.

Another embodiment consistent with the invention may comprise a systemfor providing accessing offline voicemail messages. The system maycomprise a memory storage and a processing unit coupled to the memorystorage. The processing unit may be operative to receive a voicemailmessage, download the voicemail message, transcribe the voicemailmessage to text, store the voicemail message, present a recipient with alist of voicemail messages, select a voicemail from the list, retrievethe voicemail message, allow a recipient to annotate the voicemailmessage, and synchronize the annotated voicemail message with a server.

FIG. 6 is a block diagram of a system including computing device 600.Consistent with an embodiment of the invention, the aforementionedmemory storage and processing unit may be implemented in a computingdevice, such as computing device 600 of FIG. 6. Any suitable combinationof hardware, software, or firmware may be used to implement the memorystorage and processing unit. For example, the memory storage andprocessing unit may be implemented with computing device 600 or any ofother computing devices 618, in combination with computing device 600.The aforementioned system, device, and processors are examples and othersystems, devices, and processors may comprise the aforementioned memorystorage and processing unit, consistent with embodiments of theinvention. Furthermore, computing device 600 may comprise an operatingenvironment for server 102 as described above. Server 102 may operate inother environments and is not limited to computing device 600.

With reference to FIG. 6, a system consistent with an embodiment of theinvention may include a computing device, such as computing device 600.In a basic configuration, computing device 600 may include at least oneprocessing unit 602 and a system memory 604. Depending on theconfiguration and type of computing device, system memory 604 maycomprise, but is not limited to, volatile (e.g. random access memory(RAM)), non-volatile (e.g. read-only memory (ROM)), flash memory, or anycombination. System memory 604 may include operating system 605, one ormore programming modules 606, and may include a program data 607.Operating system 605, for example, may be suitable for controllingcomputing device 600's operation. In one embodiment, programming modules606 may include a mobile messaging application 620. Furthermore,embodiments of the invention may be practiced in conjunction with agraphics library, other operating systems, or any other applicationprogram and is not limited to any particular application or system. Thisbasic configuration is illustrated in FIG. 6 by those components withina dashed line 608.

Computing device 600 may have additional features or functionality. Forexample, computing device 600 may also include additional data storagedevices (removable and/or non-removable) such as, for example, magneticdisks, optical disks, or tape. Such additional storage is illustrated inFIG. 6 by a removable storage 609 and a non-removable storage 610.Computer storage media may include volatile and nonvolatile, removableand non-removable media implemented in any method or technology forstorage of information, such as computer readable instructions, datastructures, program modules, or other data. System memory 604, removablestorage 609, and non-removable storage 610 are all computer storagemedia examples (i.e., memory storage.) Computer storage media mayinclude, but is not limited to, RAM, ROM, electrically erasableread-only memory (EEPROM), flash memory or other memory technology,CD-ROM, digital versatile disks (DVD) or other optical storage, magneticcassettes, magnetic tape, magnetic disk storage or other magneticstorage devices, or any other medium which can be used to storeinformation and which can be accessed by computing device 600. Any suchcomputer storage media may be part of device 600. Computing device 600may also have input device(s) 612 such as a keyboard, a mouse, a pen, asound input device, a touch input device, etc. Output device(s) 614 suchas a display, speakers, a printer, etc. may also be included. Theaforementioned devices are examples and others may be used.

Computing device 600 may also contain a communication connection 616that may allow device 600 to communicate with other computing devices618, such as over a network in a distributed computing environment, forexample, an intranet or the Internet. Communication connection 616 isone example of communication media. Communication media may typically beembodied by computer readable instructions, data structures, programmodules, or other data in a modulated data signal, such as a carrierwave or other transport mechanism, and includes any information deliverymedia. The term “modulated data signal” may describe a signal that hasone or more characteristics set or changed in such a manner as to encodeinformation in the signal. By way of example, and not limitation,communication media may include wired media such as a wired network ordirect-wired connection, and wireless media such as acoustic, radiofrequency (RF), infrared, and other wireless media. The term computerreadable media as used herein may include both storage media andcommunication media.

As stated above, a number of program modules and data files may bestored in system memory 604, including operating system 605. Whileexecuting on processing unit 602, programming modules 606 may performprocesses including, for example, one or more method 200's and 500'sstages as described above. The aforementioned process is an example, andprocessing unit 602 may perform other processes. Other programmingmodules that may be used in accordance with embodiments of the presentinvention may include electronic mail and contacts applications, wordprocessing applications, spreadsheet applications, databaseapplications, slide presentation applications, drawing or computer-aidedapplication programs, etc.

Generally, consistent with embodiments of the invention, program modulesmay include routines, programs, components, data structures, and othertypes of structures that may perform particular tasks or that mayimplement particular abstract data types. Moreover, embodiments of theinvention may be practiced with other computer system configurations,including hand-held devices, multiprocessor systems,microprocessor-based or programmable consumer electronics,minicomputers, mainframe computers, and the like. Embodiments of theinvention may also be practiced in distributed computing environmentswhere tasks are performed by remote processing devices that are linkedthrough a communications network. In a distributed computingenvironment, program modules may be located in both local and remotememory storage devices.

Furthermore, embodiments of the invention may be practiced in anelectrical circuit comprising discrete electronic elements, packaged orintegrated electronic chips containing logic gates, a circuit utilizinga microprocessor, or on a single chip containing electronic elements ormicroprocessors. Embodiments of the invention may also be practicedusing other technologies capable of performing logical operations suchas, for example, AND, OR, and NOT, including but not limited tomechanical, optical, fluidic, and quantum technologies. In addition,embodiments of the invention may be practiced within a general purposecomputer or in any other circuits or systems.

Embodiments of the invention, for example, may be implemented as acomputer process (method), a computing system, or as an article ofmanufacture, such as a computer program product or computer readablemedia. The computer program product may be a computer storage mediareadable by a computer system and encoding a computer program ofinstructions for executing a computer process. The computer programproduct may also be a propagated signal on a carrier readable by acomputing system and encoding a computer program of instructions forexecuting a computer process. Accordingly, the present invention may beembodied in hardware and/or in software (including firmware, residentsoftware, micro-code, etc.). In other words, embodiments of the presentinvention may take the form of a computer program product on acomputer-usable or computer-readable storage medium havingcomputer-usable or computer-readable program code embodied in the mediumfor use by or in connection with an instruction execution system. Acomputer-usable or computer-readable medium may be any medium that cancontain, store, communicate, propagate, or transport the program for useby or in connection with the instruction execution system, apparatus, ordevice.

The computer-usable or computer-readable medium may be, for example butnot limited to, an electronic, magnetic, optical, electromagnetic,infrared, or semiconductor system, apparatus, device, or propagationmedium. More specific computer-readable medium examples (anon-exhaustive list), the computer-readable medium may include thefollowing: an electrical connection having one or more wires, a portablecomputer diskette, a random access memory (RAM), a read-only memory(ROM), an erasable programmable read-only memory (EPROM or Flashmemory), an optical fiber, and a portable compact disc read-only memory(CD-ROM). Note that the computer-usable or computer-readable mediumcould even be paper or another suitable medium upon which the program isprinted, as the program can be electronically captured, via, forinstance, optical scanning of the paper or other medium, then compiled,interpreted, or otherwise processed in a suitable manner, if necessary,and then stored in a computer memory.

Embodiments of the present invention, for example, are described abovewith reference to block diagrams and/or operational illustrations ofmethods, systems, and computer program products according to embodimentsof the invention. The functions/acts noted in the blocks may occur outof the order as shown in any flowchart. For example, two blocks shown insuccession may in fact be executed substantially concurrently or theblocks may sometimes be executed in the reverse order, depending uponthe functionality/acts involved.

While certain embodiments of the invention have been described, otherembodiments may exist. Furthermore, although embodiments of the presentinvention have been described as being associated with data stored inmemory and other storage mediums, data can also be stored on or readfrom other types of computer-readable media, such as secondary storagedevices, like hard disks, floppy disks, or a CD-ROM, a carrier wave fromthe Internet, or other forms of RAM or ROM. Further, the disclosedmethods' stages may be modified in any manner, including by reorderingstages and/or inserting or deleting stages, without departing from theinvention.

All rights including copyrights in the code included herein are vestedin and the property of the Applicant. The Applicant retains and reservesall rights in the code included herein, and grants permission toreproduce the material only in connection with reproduction of thegranted patent and for no other purpose.

While the specification includes examples, the invention's scope isindicated by the following claims. Furthermore, while the specificationhas been described in language specific to structural features and/ormethodological acts, the claims are not limited to the features or actsdescribed above. Rather, the specific features and acts described aboveare disclosed as example for embodiments of the invention.

What is claimed is:
 1. A system for accessing voicemail messages, thesystem comprising: a memory having computer-readable instructions storedthereon; and a processing unit coupled to the memory, wherein uponexecution of the computer-readable instructions, the system is operativeto: receive a voicemail message generated from a call; provide a userinterface, the user interface displaying: a text transcription of thevoicemail message, wherein text corresponding to unrecognized voicemailspeech is displayed differently from text corresponding to recognizedvoicemail speech; and a play control, wherein an audio recording of thevoicemail message is played upon activating the play control.
 2. Thesystem of claim 1, the user interface further displaying: a progressbar, wherein the progress bar is displayed upon activation of the playcontrol.
 3. The system of claim 1, the user interface furtherdisplaying: a duration of the audio recording.
 4. The system of claim 1,the user interface further displaying: a delete control, wherein atleast one of the text transcription and the audio recording is deletedupon activation of the delete control.
 5. The system of claim 1, thesystem further operative to: receive a selection of a point in thetranscribed voicemail message, wherein the selected point is not a firstword of the transcribed voicemail message; and play the voicemailmessage from the selected point in the transcribed voicemail message. 6.The system of claim 1, the user interface further displaying: a controlfor playing the audio recording through an external speaker.
 7. Thesystem of claim 6, wherein the actions for selection comprise one ormore of: annotate a voicemail message; play a voicemail message; deletea voicemail message; reply to a voicemail message; flag a voicemailmessage; and call back a phone number for a voicemail message.
 8. Thesystem of claim 1, wherein the text corresponding to unrecognizedvoicemail speech is displayed differently based on one or more of afont, a color or a size of the text.
 9. The system of claim 1, thesystem further operative to: receive a selection of the voicemailmessage; receive an annotation associated with the selected voicemailmessage, the annotation including text notes; and store the annotationwith the selected voicemail message.
 10. A computer-readable storagedevice that stores a set of instructions which when executed causes acomputing device to perform a method, comprising: receiving a voicemailmessage generated from a call; providing a user interface, the userinterface displaying: a text transcription of the voicemail message,wherein text corresponding to unrecognized voicemail speech is displayeddifferently from text corresponding to recognized voicemail speech; anda play control, wherein an audio recording of the voicemail message isplayed upon activating the play control.
 11. The computer-readablestorage device of claim 10, the user interface further displaying: aprogress bar, wherein the progress bar is displayed upon activation ofthe play control.
 12. The computer-readable storage device of claim 10,the user interface further displaying: a duration of the audiorecording.
 13. The computer-readable storage device of claim 10, theuser interface further displaying: a delete control, wherein, at leastone of the text transcription and the audio recording is deleted uponactivation of the delete control.
 14. The computer-readable storagedevice of claim 10, the method further comprising receiving a selectionof a point in the transcribed voicemail message, wherein the selectedpoint is not a first word of the transcribed voicemail message; and inresponse to activation of the play control, playing the voicemailmessage from the selected point in the transcribed voicemail message.15. The computer-readable storage device of claim 10, the method furthercomprising: displaying a list of voicemail messages; and displaying oneor more actions for selection in the user interface.
 16. Thecomputer-readable storage device of claim 10, the method furthercomprising: providing a notification of at least one missed call in theuser interface,
 17. A method executed by a computing system foraccessing voicemail messages, the method comprising: receiving avoicemail message generated from a call; providing a user interface, theuser interface displaying: a text transcription of the voicemailmessage, wherein text corresponding to unrecognized voicemail speech isdisplayed differently from text corresponding to recognized voicemailspeech; and a play control, wherein an audio recording of the voicemailmessage is accessible upon activating the play control.
 18. The methodof claim 17, further comprising: receiving an annotation associated withthe voicemail message, the annotation including text notes; and storingthe annotation with the voicemail message.
 19. The method of claim 17,wherein receiving the voicemail message comprises: recognizing at leastone of a telephone number and a sender; and generating informationcomprising at least one of: an electronic mail address, a physicaladdress, a website link, the telephone number, and a name of the sender.20. The method of claim 17, wherein displaying the text corresponding tounrecognized voicemail speech differently comprises modifying one ormore of a font, a color or a size of the text.